-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rename test for k8s-labs #68
base: main
Are you sure you want to change the base?
Conversation
I'm going to nudge @corysabol on this one since he knows more about what's going on with the k8s labs. |
I will take a look later this evening when I'm back near a computer :)
…On Sat, Mar 9, 2024, 9:00 AM Jason ***@***.***> wrote:
I'm going to nudge @corysabol <https://github.com/corysabol> on this one
since he knows more about what's going on with the k8s labs.
—
Reply to this email directly, view it on GitHub
<#68 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABDBVFAZNUDSAFY6YRMBVYLYXMIYZAVCNFSM6AAAAABENJFRC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBWHA3DKMBZHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I suspect the test is failing in the runner because the minikube driver is set to I imagine the test github action is itself a docker container so getting the docker driver to work would take some tweaking most likely. In the samuraivm itself I think there was some hackery I had to do to get the docker driver to work as root. I'd like to find a better solution to this, but I also had a lot of issues when using |
I don't think the ports are correct. This is running from a VM on my local:
|
The test fails because the ports aren't mapped correctly with nginx. I can't readily tell which ports are supposed to be mapped. I had to move the nginx conf to the
start
operation because the cluster IP isn't available until minikube is started.